Vehicle automated driving system

ABSTRACT

A vehicle automated driving system  100  comprises a surrounding environment information acquiring device  10 , a vehicle information acquiring device  20 , a driver information acquiring device  30 , a package selecting part  90 , a package proposing part  91 , an automated driving executing part  92 , and a rejection count detecting part  93 . The package selecting part determines the driving assistance package based on at least one of the surrounding environment information, the vehicle information, and the driver information, selects the determined driving assistance package if the rejection count of the determined driving assistance package is less than a predetermined threshold value, and selects a driving assistance package different from the determined driving assistance package if the rejection count of the determined driving assistance package is the threshold value or more.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.16/851,391 filed Apr. 17, 2020, which is a continuation of U.S.application Ser. No. 15/495,037 filed Apr. 24, 2017, which claimspriority from Japanese Patent Application No. 2016-089116 filed Apr. 27,2016. The entire disclosures of the prior applications are consideredpart of the disclosure of the accompanying continuation application, andare hereby incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present invention relates to a vehicle automated driving system.

BACKGROUND ART

PLT 1 discloses a conventional vehicle automated driving system whereinwhen a driver operates a switch to change from a manual driving mode toan automated driving mode, automated driving is performed includingvehicle distance control, lane tracking control, and other variousdriving assistance operations performed automatically.

CITATIONS LIST Patent Literature

PLT 1: U.S. Pat. No. 8,670,891 PLT 2: Japanese Patent Publication No.11-102157A PLT 3: Japanese Patent Publication No. 09-086223A

SUMMARY OF INVENTION Technical Problem

However, the above-mentioned conventional vehicle control system usedthe fact of the automated driving mode being switched to so as to judgethat the driver had given permission for all driving assistanceoperations. For this reason, when performing automated driving, thedriver was only able to switch from the manual driving mode to theautomated driving mode and could not freely set permissions for theindividual driving assistance operations in accordance with thepreferences of the driver. However, to keep driving assistanceoperations not required by the driver from being performed, it ispreferable to enable the driver to freely set permissions for individualdriving assistance operations at the time of automated driving.

On the other hand, if a driver could freely set permissions forindividual driving assistance operations at the time of automateddriving, the operation by the driver for setting the system would becometroublesome. Further, in poor weather and other predeterminedsurrounding environment conditions, some driving assistance operationscould be difficult.

Therefore, an object of the present invention is to provide an automateddriving system enabling a driver to easily set permissions forindividual driving assistance operations in automated driving inaccordance with the preferences of the driver, the surroundingenvironment conditions etc.

In order to solve the above problem, in a first aspect, there isprovided A vehicle automated driving system comprising: a surroundingenvironment information acquiring device acquiring surroundingenvironment information relating to surrounding environment conditionsof the vehicle; a vehicle information acquiring device acquiring vehicleinformation relating to conditions of the vehicle; a driver informationacquiring device acquiring driver information relating to conditions ofa driver of the vehicle; a package selecting part selecting a drivingassistance package packaging permissions for a plurality of drivingassistance operations; a package proposing part proposing the drivingassistance package selected by the package selecting part to the driver;an automated driving executing part executing driving assistanceoperations for which performance is permitted in the driving assistancepackage proposed by the packaging proposing part and approved by thedriver; and a rejection count detecting part judging whether performanceof driving assistance operations for which performance is permitted in adriving assistance package has been rejected by the driver and detectingthe number of times performance of driving assistance operations forwhich performance is permitted in the driving assistance package hasbeen rejected by the driver as the rejection count of the drivingassistance package, wherein the package selecting part determines thedriving assistance package based on at least one of the surroundingenvironment information, the vehicle information, and the driverinformation, selects the determined driving assistance package if therejection count of the determined driving assistance package is lessthan a predetermined threshold value, and selects a driving assistancepackage different from the determined driving assistance package if therejection count of the determined driving assistance package is thethreshold value or more.

In a second aspect, the rejection count detecting part judges thatperformance of driving assistance operations for which performance ispermitted in the driving assistance package has been rejected by thedriver, if the driving assistance package proposed by the packageproposing part was not approved by the driver, in the first aspect.

In a third aspect, the rejection count detecting part judges thatperformance of driving assistance operations for which performance ispermitted in the driving assistance package has been rejected by thedriver, if performance of driving assistance operations for whichperformance is permitted in the driving assistance package wasobstructed by an input operation performed by the driver, in the firstor second aspect.

In a forth aspect, the input operation performed by the driver is atleast one of acceleration, steering, and braking, in the third aspect.

In a fifth aspect, the package selecting part selects a drivingassistance package in which performance of driving assistance operationswhose performance is obstructed by the input operation performed by thedriver is not permitted, if the rejection count of the determineddriving assistance package is the threshold value or more, in the thirdor fourth aspect.

In a sixth aspect, the system further comprises a driver identifyingpart identifying the driver of the vehicle based on the driverinformation, and the rejection count detecting part judges whetherperformance of driving assistance operations for which performance ispermitted in a driving assistance package has been rejected by thedriver identified by the driver identifying part, and detects the numberof times performance of driving assistance operations for whichperformance is permitted in the driving assistance package has beenrejected by the driver identified by the driver identifying part as therejection count of the driving assistance package, in any one of thefirst to fifth aspects.

Advantageous Effects of Invention

According to the present invention, there is provided an automateddriving system enabling a driver to easily set permissions forindividual driving assistance operations in automated driving inaccordance with the preferences of the driver, the surroundingenvironment conditions etc.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram showing the configuration of a vehicleautomated driving system according to a first embodiment of the presentinvention.

FIG. 2 is a schematic side view of a vehicle equipped with an automateddriving system.

FIG. 3 is a view schematically showing the inside of a vehicle equippedwith an automated driving system.

FIG. 4 is a view showing a list of driving assistance operationsperformed during an automated driving mode by an automated drivingsystem.

FIG. 5 is a view showing a group of packages relating to weatherconditions.

FIG. 6 is a view showing a group of packages relating to sunlightconditions.

FIG. 7 is a view showing a group of packages relating to road types.

FIG. 8 is a view showing a group of packages relating to roadconditions.

FIG. 9 is a view showing a group of packages relating to driverconditions.

FIG. 10 is a view showing a group of packages relating to home vehicleconditions.

FIG. 11 is a flow chart showing a control routine of vehicle control inthe first embodiment of the present invention.

FIG. 12 is a flow chart showing a control routine of driving assistancepackage selection processing in the first embodiment of the presentinvention.

FIG. 13 is a map showing a priority degree of switching of unit packagesin a group of packages relating to weather conditions.

FIG. 14 is a map showing a priority degree of a group of packages inwhich unit packages are switched.

FIG. 15 is a flow chart showing a control routine of rejection countdetection processing in the first embodiment of the present invention.

FIG. 16 is a flow chart of a control routine of priority degree changingprocessing in a second embodiment of the present invention.

FIG. 17 is a block diagram showing the configuration of an automateddriving system of a vehicle according to a third embodiment of thepresent invention.

FIG. 18 is a flow chart of a control routine of rejection countdetection processing in the third embodiment of the present invention.

FIG. 19 is a flow chart of a control routine of driving assistancepackage selection processing in the third embodiment of the presentinvention.

DESCRIPTION OF EMBODIMENTS

Below, referring to the drawings, embodiments of the present inventionwill be explained in detail. Note that, in the following explanation,similar components are assigned the same reference notations.

First Embodiment

First, referring to FIG. 1 to FIG. 15, a first embodiment of the presentinvention will be explained.

Configuration of Automated Driving System

FIG. 1 is a block diagram showing the configuration of a vehicleautomated driving system 100 according to the first embodiment of thepresent invention. FIG. 2 is a schematic side view of a vehicle 1equipped with an automated driving system 100. FIG. 3 is a viewschematically showing the inside of a vehicle 1 equipped with anautomated driving system 100.

As shown in FIG. 1, the automated driving system 100 is provided with asurrounding environment information acquiring device 10, vehicleinformation acquiring device 20, driver information acquiring device 30,map database 40, storage device 50, human machine interface (HMI) 60,navigation system 70, and electronic control unit (ECU) 80.

The surrounding environment information acquiring device 10 acquiressurrounding environment information relating to the conditions of thesurrounding environment of the vehicle 1. The surrounding environmentinformation includes the weather, the road on which the vehicle 1 isrunning, obstacles around the vehicle 1 (curbs, buildings, othervehicles, pedestrians, fallen objects, etc.) and other information. Thesurrounding environment information acquiring device 10 is provided witha LIDAR (laser imaging detection and ranging device) 11, milliwave radarsensors 12, an outside camera 13, a luminance sensor 14, a rain sensor15, and an external information receiving apparatus 16.

The LIDAR 11 uses laser light to detect the road and obstacles in thesurroundings of the vehicle 1. As shown in FIG. 2, in the presentembodiment, the LIDAR 11 is attached to the roof of the vehicle 1. TheLIDAR 11 successively irradiates laser light toward the entiresurroundings of the vehicle 1 and measures the distances to the road andobstacles from the reflected light. The LIDAR 11 generates 3D images ofthe road and obstacles in the entire surroundings of the vehicle 1 basedon the measurement results, and transmits the generated 3D imageinformation as surrounding environment information to the electroniccontrol unit 80. Note that, the position where the LIDAR 11 is mountedto the vehicle 1 may be a position different from the position shown inFIG. 2.

The milliwave radar sensors 12 use electrical waves to detect obstaclesaround the vehicle 1 over a further distance than the LIDAR 11. As shownin FIG. 2, in the present embodiment, the milliwave radar sensors 12 areattached to the front bumper and rear bumper of the vehicle 1. Themilliwave radar sensors 12 emit electrical waves to the surroundings ofthe vehicle 1 (in the present embodiment, to the front, rear, and sidesof the vehicle 1) and measure the distances to obstacles in thesurroundings of the vehicle 1 and relative speeds with the obstaclesfrom the reflected waves. The milliwave radar sensors 12 transmit theresults of measurement as surrounding environment information to theelectronic control unit 80.

Note that, the positions where the milliwave radar sensors 12 areattached to the vehicle 1 are not limited to the positions shown in FIG.2 so long as positions enabling the necessary surrounding environmentinformation to be acquired. For example, the milliwave radar sensors 12may also be attached to the grilles of the vehicle 1 or the insides ofthe vehicle lights (for example headlights or brake lights) or thechassis part (frame) of the vehicle 1.

The outside camera 13 captures an image of the field in front of thevehicle 1. As shown in FIG. 2, in the present embodiment, the outsidecamera 13 is attached to the center of the front end of the roof of thevehicle 1. The outside camera 13 performs image processing of thecaptured image to detect information on obstacles in front of thevehicle 1, traffic information in the surroundings of the vehicle 1(lane width, road shape, road signs, white lines, statuses of trafficlights, etc.), the yaw angle (relative direction of vehicle 1 to runninglane), running information of vehicle 1 (for example, offset of vehicle1 from center of running lane), meteorological information in thesurroundings of vehicle 1 (information on rain, snow, fog, etc.), etc.The outside camera 13 transmits the detected information as surroundingenvironment information to the electronic control unit 80.

Note that, the position where the outside camera 13 is mounted at thevehicle 1 is not limited to the position shown in FIG. 2 so long as aposition able to capture an image of the field in front of the vehicle1. For example, the outside camera 13 may be attached to the top centerof the back surface of the windshield at the inside of the vehicle 1.

The luminance sensor 14 detects the luminance of the surroundings of thevehicle 1. As shown in FIG. 2, in the present embodiment, the luminancesensor 14 is attached to the top surface of an instrument panel in thevehicle 1. The luminance sensor 14 transmits the detected luminanceinformation of the surroundings of the vehicle 1 as surroundingenvironment information to the electronic control unit 80. Note that,the position where the luminance sensor 14 is mounted at the vehicle 1may be a position different from the position shown in FIG. 3.

The rain sensor 15 detects the presence of rainfall and the amount ofrainfall. As shown in FIG. 2, in the present embodiment, the rain sensor15 is attached to the top center of the front surface of the windshieldof the vehicle 1. The rain sensor 15 emits light generated from abuilt-in light emitting diode toward the front surface of the windshieldand measures the change of the reflected light at that time so as todetect rainfall information such as the presence of rainfall and theamount of rainfall. The rain sensor 15 transmits the detected rainfallinformation as surrounding environment information to the electroniccontrol unit 80. Note that, the position where the rain sensor 15 isattached to the vehicle 1 may be a position different from the positionshown in FIG. 2.

The external information receiving apparatus 16 receives, for example,congestion information and meteorological information (weather, airtemperature, wind speed, and other information) and other such externalinformation sent from a road traffic information communication systemcenter or other external communication center. The external informationreceiving apparatus 16 transmits the received external information assurrounding environment information to the electronic control unit 80.

The vehicle information acquiring device 20 acquires vehicle informationrelating to the conditions of the vehicle 1 (host vehicle). The vehicleinformation includes the speed, acceleration, posture, current position,and other information of the vehicle 1. As shown in FIG. 1, the vehicleinformation acquiring device 20 is provided with a speed sensor 21, anacceleration sensor 22, a yaw rate sensor 23, and a GPS receiver 24.

The speed sensor 21 detects the speed of the vehicle 1. The speed sensor21 transmits the detected speed of the vehicle 1 as vehicle informationto the electronic control unit 80.

The acceleration sensor 22 detects the acceleration of the vehicle 1 atthe time of acceleration and the time of braking. The accelerationsensor 22 transmits the detected acceleration of the vehicle 1 asvehicle information to the electronic control unit 80.

The yaw rate sensor 23 detects the posture of the vehicle 1.Specifically, the yaw rate sensor 23 detects the speed of change of theyaw angle at the time of turning of the vehicle 1, that is, therotational angle speed (yaw rate) around the vertical axis of thevehicle 1. The yaw rate sensor 23 transmits the detected posture of thevehicle 1 as vehicle information to the electronic control unit 80.

The GPS receiver 24 receives signals from three or more GPS satellites,identifies the latitude and longitude of the vehicle 1, and detects thecurrent position of the vehicle 1. The GPS receiver 24 transmits thedetected current position of the vehicle 1 as vehicle information to theelectronic control unit 80.

The driver information acquiring device 30 acquires driver informationrelating to the conditions of the driver of the vehicle 1. The driverinformation includes the facial expression, posture, etc. of the driver.As shown in FIG. 1, the driver information acquiring device 30 isprovided with a driver monitor camera 31 and a steering wheel touchsensor 32.

The driver monitor camera 31 captures an image of the appearance of thedriver. As shown in FIG. 3, in the present embodiment, the drivermonitor camera 31 is attached to the top surface of a steering wheelcolumn cover. The driver monitor camera 31 performs image processing ofthe captured image of the driver so as to detect the facial expressionof the driver (direction of face of driver, line of sight, degree ofopening of eyes, etc.), posture, and other appearance information of thedriver. The driver monitor camera 31 transmits the detected appearanceinformation of the driver as driver information to the electroniccontrol unit 80. Note that, the position at which the driver monitorcamera 31 is attached to the vehicle 1 may be a position different fromthe position shown in FIG. 3.

The steering wheel touch sensor 32 detects if the driver is gripping thesteering wheel. As shown in FIG. 3, the steering wheel touch sensor 32is attached to the steering wheel. The steering wheel touch sensor 32transmits the detected gripping information of the steering wheel asdriver information to the electronic control unit 80. Note that, theposition at which the steering wheel touch sensor 32 is attached to thevehicle 1 may be a position different from the position shown in FIG. 3.

The map database 40 is a database relating to map information. The mapdatabase 40 is, for example, stored in a hard disk drive (HDD) carriedin the vehicle 1. The map information includes position information ofthe road, shape information of the road (for example, differentiationbetween curves and straight parts, curvature of curves, etc.), positioninformation of intersections and junctions, road types, and otherinformation.

The storage device 50 stores automated driving road maps. The automateddriving road maps are prepared by the electronic control unit 80 basedon the 3D image generated by the LIDAR 11. The electronic control unit80 updates the automated driving road maps constantly or periodically.

The HMI 60 is an interface for input and output of information betweenthe driver or vehicle passenger and the automated driving system 100.The HMI 60, for example, includes a display displaying text or imageinformation, a speaker generating sound, operating buttons for thedriver or vehicle passenger to input operations, a touch panel, amicrophone, etc.

The navigation system 70 guides the vehicle 1 to a destination set bythe driver through the HMI 60. The navigation system 70 calculates thetarget route to the target destination based on the current positioninformation of the vehicle 1 detected by the GPS receiver 24 and the mapinformation of the map database 40. The navigation system 70 transmitsthe calculated information relating to the target route as navigationinformation to the electronic control unit 80.

The electronic control unit 80 is a microcomputer provided withcomponents connected with each other by bidirectional buses such as acenter processing unit (CPU), read only memory (ROM), random accessmemory (RAM), input port, and output port. The electronic control unit80 outputs control signals for controlling various actuators forperforming individual driving assistance operations from the output portto control the vehicle 1 based on surrounding environment information,vehicle information, driver information, navigation information, andother various information required for automated driving, which areinput to the electronic control unit 80.

Explanation of Driving Assistance Operations in Automated Driving

FIG. 4 is a view showing a list of driving assistance operationsperformed in the automated driving mode by the automated driving system100 in the present embodiment. In the present embodiment, the drivingassistance operations are roughly divided into three groups of functionsof running assistance functions, vision assistance functions, andcongestion assistance functions.

The driving assistance operations grouped together in the section ofrunning assistance functions are driving assistance operations havingfunctions for performing at least one of acceleration, steering, andbraking (running assistance functions). In the present embodiment, asdriving assistance operations having running assistance functions,vehicle distance control, lane tracking control, auto lane change, autopassing, auto branching, and auto merging may be mentioned. However, thetypes and numbers of the driving assistance operations having runningassistance functions may differ from those shown in FIG. 4.

Note that, “vehicle distance control” is control automatically adjustingthe vehicle speed within the range of a limit speed so as to be able tomaintain a suitable vehicle distance corresponding to the vehicle speedwhile tracking a preceding vehicle in response to the change of vehiclespeed of the preceding vehicle. “Lane tracking control” is controlautomatically adjusting the steering amount or vehicle speed so that thevehicle 1 runs on a suitable running line corresponding to the lanewidth of the running lane.

The driving assistance operations grouped together in the section ofvision assistance functions are driving assistance operations havingfunctions of securing the field of vision of the driver and in turnsafety (vision assistance functions) among driving assistance operationsnot having running assistance functions (that is, not performing any ofacceleration, steering, and braking). In the present embodiment, asdriving assistance operations having vision assistance functions, lanedeparture warning, blind spot monitoring, and other of eleven drivingassistance operations may be illustrated. However, the types and numbersof the driving assistance operations having vision assistance functionsmay differ from those shown in FIG. 4.

The driving assistance operations grouped together in the section ofcongestion assistance functions are driving assistance operations havingfunctions of easing fatigue of the driver and vehicle passengers at thetime of congestion (congestion assistance functions). In the presentembodiment, as driving assistance operations having congestionassistance functions, auto start from stopping at the time of congestionand control for temporarily turning on the hazard light and other ofeight driving assistance operations may be illustrated. However, thetypes and numbers of the driving assistance operations having congestionassistance functions may differ from those shown in FIG. 4.

In this regard, it is preferable for the driver to be able to freely setpermissions for individual driving assistance operations before thestart of automated driving and during automated driving so that drivingassistance operations not required by the driver are not automaticallyperformed at the time of automated driving. On the other hand, if thedriver sets permissions for individual driving assistance operations atautomated driving one at a time, the operation by the driver for settingthe system would become troublesome and in turn the convenience ofautomated driving would fall. Further, the conditions of the surroundingenvironment, conditions of the host vehicle, and conditions of thedriver change at each instant while the vehicle is running. Situationsarise where some driving assistance operations become difficult (forexample, poor weather etc.)

Explanation of Driving Assistance Package

Therefore, in the present embodiment, a driving assistance package whichpackages permissions for a plurality of driving assistance operations isdetermined based on at least one of the surrounding environmentinformation, host vehicle information, and driver information, and thedetermined driving assistance package is proposed to the driver.Specifically, unit packages suitable for the weather conditions,sunlight conditions, road types, road conditions, driver conditions, andhost vehicle conditions are selected from the groups of packages shownin FIG. 5 to FIG. 10 and a driving assistance package combining theselected unit packages is proposed to the driver. The driving assistancepackage sets permissions for different driving assistance operations.

Below, referring to FIG. 5 to FIG. 10, the groups of packages will beexplained. Note that, in FIG. 5 to FIG. 10, the O marks show permissionto perform the driving assistance operations, while the X marks show nopermission to perform the driving assistance operations. Further, thegroups of packages are stored in the ROM of the electronic control unit80.

FIG. 5 is a view showing the group of packages relating to theconditions of the weather. The group of packages relating to the weatherconditions roughly divides weather conditions into the nine conditionsof “clear”, “rain”, “heavy rain”, “snow”, “heavy snow”, “fog”, “thickfog”, “wind”, and “strong wind” and packages permissions for individualdriving assistance operations for each of the weather conditions. Forthis reason, the group of packages relating to the weather conditionsincludes nine unit packages. In the present embodiment, the weatherconditions during automated driving are specified based on themeteorological information around the vehicle 1 detected by the outsidecamera 13 and the meteorological information included in externalinformation received by the external information receiving apparatus 16.

FIG. 6 is a view showing the group of packages relating to theconditions of sunlight. The group of packages relating to the sunlightconditions roughly divides sunlight conditions into “day” and “night”and packages permissions for individual driving assistance operationsfor each of the sunlight conditions. For this reason, the group ofpackages relating to the sunlight conditions includes two unit packages.In the present embodiment, the sunlight conditions during automateddriving are specified based on the luminance information detected by theluminance sensor 14 and the time of day.

FIG. 7 is a view showing the group of packages relating to the types ofthe road. The group of packages relating to the road type roughlydivides road types into the four types of “general roads”, “trunkroads”, “inter-city highways” (Tokyo-Nagoya highway, Nagoya-Kobehighway, etc.), and “city highways” (Tokyo metropolitan highway andOsaka-Kobe highway etc.) and packages permissions for individual drivingassistance operations for each of the road types. For this reason, thegroup of packages relating to the road types includes four unitpackages. In the present embodiment, the road type during automateddriving is specified based on the traffic information around the vehicle1 detected by the outside camera 13 and the road type informationcontained in the map information of the map database 40.

FIG. 8 is a view showing the group of packages relating to theconditions of the road. The group of packages relating to the roadconditions roughly divides the road conditions into congested andnoncongested and packages permissions for individual driving assistanceoperations for each of the road conditions. For this reason, the groupof packages relating to the road conditions includes two unit packages.In the present embodiment, the road conditions during automated drivingare specified based on the information of the 3D image generated by theLIDAR 11, the surrounding environment information detected by themilliwave radar sensors 12, the information on obstacles in front of thevehicle 1 detected by the outside camera 13 and traffic informationaround the vehicle 1, the congestion information included in theexternal information received by the external information receivingapparatus 16, and the speed of the vehicle 1 detected by the speedsensor 21.

Note that, in the present embodiment, “congested” means a conditionwhere there is another vehicle around the vehicle 1 (preceding vehicleor following vehicle) and the speeds of the vehicle 1 and the othervehicle around the vehicle 1 are sustained constant speeds (for example,on general roads and trunk roads, 20 km/h and on inter-city highways andcity highways, 40 km/h) or less. On the other hand, “noncongested” meansa condition other than “congested”.

FIG. 9 is a view showing a group of packages relating to the conditionsof the driver. The group of packages relating to the driver conditionsroughly divides the driver conditions into the five conditions of“sleepy”, “tired”, “overworked”, “distracted”, and “normal” and packagespermissions for individual driving assistance operations for each of thedriver conditions. For this reason, the group of packages relating tothe driver conditions includes five unit packages. In the presentembodiment, the driver conditions during automated driving are specifiedby the information of the appearance of the driver detected by thedriver monitor camera 31 and information of gripping of the steeringwheel detected by the steering wheel touch sensor 32. Specifically, thedriver conditions are specified by detecting the facial expression ofthe driver (direction of face, degree of opening/closing of the eyes,etc.) from the information on the appearance of the driver whilereferring to the information of gripping of the steering wheel andcomparing the detected expression of the driver with an expressionaccording to the driver conditions stored in the ROM in advance.

Note that, the parameters for specifying driver conditions are notlimited to the information on the appearance of the driver andinformation of gripping of the steering wheel. For example, it is alsopossible to detect the heartbeat, pulse, brainwave, etc. of the driverand compare the same with the heartbeat, pulse, brainwave, etc.corresponding to the driver conditions stored in advance in the ROM soas to specify the driver conditions. In this case, the driverinformation acquiring device is provided with a heartbeat sensor, apulse sensor, a brainwave sensor, etc.

Note that, in the present embodiment, “sleepy” means a condition wherethe concentration of the driver in the driving operation has fallen dueto sleepiness but not to an extent requiring the driver to immediatelystop driving. “Tired” means a condition where the concentration of thedriver in the driving operation has fallen due to tiredness but not toan extent requiring the driver to immediately stop driving. “Overworked”means a condition where the concentration of the driver in the drivingoperation has fallen due to tiredness to an extent requiring the driverto immediately stop driving. “Distracted” means, for example, when thedriver is performing a second task other than the driving operation suchas operating a mobile phone, tablet PC, or other mobile device or isviewing a moving image, when the driver is looking at the sides, andother conditions where the concentration of the driver in the drivingoperation has fallen due to factors other than sleepiness and tiredness.“Normal” means a condition other than “sleepy”, “tired”, “overworked”,and “distracted”.

FIG. 10 is a view showing the group of packages relating to theconditions of the host vehicle. The group of packages relating to thehost vehicle conditions roughly divides the host vehicle conditions into“unstable” and “stable” and packages permissions for individual drivingassistance operations for each vehicle condition. For this reason, thegroup of packages relating to the host vehicle conditions includes twounit packages. In the present embodiment, the host vehicle conditionsare specified based on the acceleration of the vehicle 1 detected by theacceleration sensor 22 and the posture of the vehicle 1 detected by theyaw rate sensor 23

Note that, in the present embodiment, the “unstable” of the host vehicleconditions means a condition where pitching, rolling, yawing, etc. ofthe vehicle 1 are continuing and the behavior of the vehicle 1 isdisturbed. “Pitching” means the vehicle rocking to the front and backabout the horizontal axis in the left-right direction passing throughthe center of gravity of the vehicle. “Rolling” means the vehiclerocking to the left and right about the horizontal axis in thefront-back direction passing through the center of gravity of thevehicle. “Yawing” means the vehicle rocking to the left and right aboutthe vertical axis passing through the center of gravity of the vehicle.On the other hand, “stable” of the host vehicle conditions means acondition other than unstable conditions, that is, a condition wherepitching, rolling, yawing, etc. of the vehicle 1 do not occur and thebehavior of the vehicle 1 is not disturbed.

<Control by Automated Driving System>

The automated driving system 100 is further provided with a packageselecting part 90, a package proposing part 91, an automated drivingexecuting part 92, and a rejection count detecting part 93. In thisembodiment, as shown in FIG. 1, the package selecting part 90, packageproposing part 91, automated driving executing part 92 and rejectioncount detecting part 93 are a part of the electronic control unit 80.

The package selecting part 90 selects a driving assistance packagepackaging permissions for a plurality of driving assistance operations.As explained above, a driving assistance package sets permissions fordifferent driving assistance operations. The package proposing part 91proposes the driving assistance package selected by the packageselecting part 90 to the driver. The automated driving executing part 92performs automated driving of the vehicle 1 based on the drivingassistance package proposed by the package proposing part 91 andapproved by the driver. Specifically, the automated driving executingpart 92 performs driving assistance operations for which performance ispermitted in the driving assistance package proposed by the packageproposing part 91 and approved by the driver.

The rejection count detecting part 93 judges whether performance of thedriving assistance operations for which performance is permitted in thedriving assistance package has been rejected by the driver, and detectsthe number of times performance of the driving assistance operations forwhich performance is permitted in the driving assistance package hasbeen rejected by the driver as the rejection count of the drivingassistance package. Specifically, the rejection count detecting part 93judges that performance of the driving assistance operations for whichperformance is permitted in the driving assistance package has beenrejected by the driver, if the driving assistance package proposed bythe package proposing part 91 was not approved by the driver.

Further, the rejection count detecting part 93 also judges thatperformance of driving assistance operations for which performance ispermitted in the driving assistance package has been rejected by thedriver, if performance of driving assistance operations for whichperformance is permitted in the driving assistance package wasobstructed by an input operation performed by the driver. The inputoperation performed by the driver includes, for example, operation of aswitch, voice input, acceleration (operation of accelerator), steering(operation of steering wheel), braking (operation of brake), etc.Therefore, for example, the rejection count detecting part 93 judgesthat performance of the driving assistance operations for whichperformance is permitted in the driving assistance package has beenrejected by the driver when override occurs during execution of thedriving assistance operations for which performance is permitted in thedriving assistance package. Note that, “override” means at least oneoperation of acceleration, steering, and braking performed by the driverresulting in the performance of the driving assistance operations beingobstructed. As a more specific example, if the driver performs steeringand obstructs change of lane of the vehicle when a driving assistanceoperation for change of lane of the vehicle is being performed, therejection count detecting part 93 judges that performance of the drivingassistance operation for which performance is permitted in the drivingassistance package has been rejected by the driver.

The package selecting part 90 determines the driving assistance packagebased on at least one of the surrounding environment information,vehicle information, and driver information, selects the determineddriving assistance package if the rejection count of the determineddriving assistance package is less than a predetermined threshold value,and selects a driving assistance package different from the determineddriving assistance package if the rejection count of the determineddriving assistance package is the threshold value or more. Thesurrounding environment information is acquired by the surroundingenvironment information acquiring device 10, the vehicle information isacquired by the vehicle information acquiring device 20, and the driverinformation is acquired by the driver information acquiring device 30.Further, the rejection count of the determined driving assistancepackage is detected by the rejection count detecting part 93. Thethreshold value is an integer of 1 or more.

Due to the above-mentioned control, a driving assistance packagecorresponding to the preferences of the driver and the surroundingenvironment information etc. is selected by the package selecting part90 and proposed to the driver by the package proposing part 91. Thedriver can set permissions for performing the different drivingassistance operations at one time by just approving the drivingassistance package proposed by the package proposing part 91. Therefore,the driver can easily set permissions for different driving assistanceoperations in automated driving in accordance with the preferences ofthe driver and surrounding environment conditions etc.

Control Routine of Vehicle Control

Below, referring to the flow chart of FIG. 11, vehicle control by theautomated driving system 100 will be explained in detail. FIG. 11 is aflow chart showing a control routine of vehicle control in a firstembodiment of the present invention. The control routine is repeatedlyexecuted by the electronic control unit 80 at predetermined timeintervals while the automated driving mode is selected by driver.

The automated driving mode and manual driving mode are switched by thedriver. Note that, the “automated driving mode” is the operating modewhere at least one of the driving operations relating to acceleration,steering, and braking is performed by the automated driving system 100.Further, the “manual driving mode” is the operating mode where alldriving operations relating to acceleration, steering, and braking areperformed by the driver.

First, at step S101, the automated driving executing part 92 judgeswhether one or more of the surrounding environment conditions,conditions of the vehicle, and conditions of the driver have changedbased on the surrounding environment information, vehicle information,and driver information. The surrounding environment information isacquired by the surrounding environment information acquiring device 10,the vehicle information is acquired by the vehicle information acquiringdevice 20, and the driver information is acquired by the driverinformation acquiring device 30. For example, if the weather conditionsaround the vehicle 1 detected by the outside camera 13 change from clearto rain, it is judged that the surrounding environment conditions havechanged.

If at step S101 it is judged that one or more of the surroundingenvironment conditions, conditions of the vehicle, and conditions of thedriver have not changed, the control routine proceeds to step S106. Atstep S106, the automated driving executing part 92 maintains the currentdriving assistance package.

Next, at step S107, the automated driving executing part 92 performs theautomated driving of the vehicle 1 based on the driving assistancepackage maintained at step S106. Specifically, the automated drivingexecuting part 92 performs the driving assistance operations for whichperformance is permitted in the driving assistance package maintained atstep S106. After step S107, the control routine is ended.

On the other hand, if at step S101 it is judged that one or more of thesurrounding environment conditions, conditions of the vehicle, andconditions of the driver have changed, the control routine proceeds tostep S102. At step S102, the later explained driving assistance packageselection processing is performed, and the package selecting part 90selects the driving assistance package. Next, at step S103, the packageproposing part 91 proposes the driving assistance package selected atstep S102 to the driver.

Next, at step S104, the automated driving executing part 92 judgeswhether the proposed driving assistance package has been approved by thedriver. If it is judged that the proposed driving assistance package hasbeen approved by the driver, the control routine proceeds to step S105.At step S105, the automated driving executing part 92 switches thedriving assistance package to the driving assistance package proposed bythe package proposing part 91 and approved by the driver.

Next, at step S107, the automated driving executing part 92 performsautomated driving of the vehicle 1 based on the driving assistancepackage switched at step S105. Specifically, the automated drivingexecuting part 92 performs the driving assistance operations for whichperformance is permitted in the driving assistance package switched toat step S105. After step S107, the control routine is ended.

On the other hand, if at step S104 it was judged that the proposeddriving assistance package was not approved by the driver, the controlroutine proceeds to step S106. At step S106, the current drivingassistance package is maintained, and at step S107, automated driving isperformed based on the maintained driving assistance package. After stepS107, the control routine is ended.

Driving Assistance Package Selection Processing

Below, referring to the flow chart of FIG. 12, the driving assistancepackage selection processing executed at step S102 of FIG. 11 will beexplained. FIG. 12 is a flow chart showing the control routine ofdriving assistance package selection processing in the first embodimentof the present invention.

First, at step S201, the package selecting part 90 acquires surroundingenvironment information, vehicle information, and driver information.The surrounding environment information is acquired from the surroundingenvironment information acquiring device 10, the vehicle information isacquired from the vehicle information acquiring device 20, and thedriver information is acquired from the driver information acquiringdevice 30. Next, at step S202, the package selecting part 90 determinesthe driving assistance package based on the surrounding environmentinformation, vehicle information, and driver information acquired atstep S201.

Specifically, the package selecting part 90 first specifies theconditions of the surrounding environment (in the present embodiment,conditions of the weather, conditions of sunlight, type of road, andconditions of the road), conditions of the host vehicle, and conditionsof the driver based on the surrounding environment information, vehicleinformation, and driver information. Next, the package selecting part 90selects the unit package of the weather condition specified as thecurrent weather condition from the group of packages relating to theweather conditions. For example, the package selecting part 90 selectsthe unit package of “heavy rain” from the group of packages relating tothe weather conditions when specifying that the current weathercondition are “heavy rain”. Similarly, the package selecting part 90selects the unit package of the sunlight condition specified as thecurrent sunlight condition from the group of packages relating to thesunlight conditions, selects the unit package of the road type specifiedas the road type currently being run on from the group of packagesrelating to the road types, selects the unit package of the roadcondition specified as the current road condition from the group ofpackages relating to the road conditions, selects the unit package ofthe driver condition specified as the current driver condition from thegroup of packages relating to the driver conditions, and selects theunit package of the host vehicle condition specified as the current hostvehicle condition from the group of package relating to the host vehicleconditions.

After selection of the unit packages, the package selecting part 90determines the driving assistance package by combining the selected unitpackages. At this time, in the present embodiment, the runningassistance functions are combined by AND conditions and the visionassistance functions and congestion assistance functions are combined byOR conditions. Therefore, regarding driving assistance operationsrelating to the running assistance functions, driving assistanceoperations permitted in all unit packages are permitted in the drivingassistance package. On the other hand, driving assistance operationswhich are not performed in one or more unit packages are not permittedin the driving assistance package.

Further, regarding driving assistance operations relating to the visionassistance functions and congestion assistance functions, drivingassistance operations permitted in one or more unit packages arepermitted in the driving assistance package. Further, driving assistanceoperations permitted in all unit packages are also permitted in thedriving assistance package. On the other hand, driving assistanceoperations which are not permitted in all unit packages are notpermitted in the driving assistance package.

In this way, in the present embodiment, the running assistance functionsare combined by AND conditions while the vision assistance functions andcongestion assistance functions are combined by OR conditions, but themethods of combinations are not limited. Combination by AND conditionsor OR conditions in accordance with need is also possible. Further, allfunctions may be combined by AND conditions or OR conditions.

Next, at step S203, the package selecting part 90 judges whether therejection count Cn of the driving assistance package determined at stepS202 is less than a threshold value Cth. The rejection count Cn isdetected by the rejection count detecting part 93 in the control routineof the rejection count detection processing explained later. “n” of therejection count Cn is the package number corresponding to the drivingassistance package determined at step S202. Further, the threshold valueCth is a predetermined integer of 1 or more.

If at step S203 it is judged that the rejection count Cn is less thanthe threshold value Cth, the control routine proceeds to step S204. Atstep S204, the package selecting part 90 selects the driving assistancepackage determined at step S202. After step S204, the control routine isended.

On the other hand, if at step S203 it is judged that the rejection countCn is the threshold value Cth or more, the control routine proceeds tostep S205. In this case, it is considered that the driving assistancepackage determined at step S202 does not match the preferences of thedriver. For this reason, at step S205, the package selecting part 90selects a driving assistance package different from the drivingassistance package determined at step S202.

For example, if the unit package of “wind” was included in the drivingassistance package determined at step S202, the package selecting part90 newly selects a driving assistance package including the unit packageof “strong wind” instead of “wind”. At this time, the priority degree ofthe unit package switched with the unit package currently included maybe predetermined.

FIG. 13 is a map showing the priority degree of switching of unitpackages in the group of packages relating to weather conditions. Inthis map, the smaller the numerical value in the column in which a unitpackage is described, the higher the priority degree for switching withthe unit package of the column at the leftmost side. For example, forthe unit package of “clear”, the unit package with the highest prioritydegree of switching is the unit package of “wind”, while the unitpackage with the lowest priority degree of switching is the unit packageof “heavy snow”. In this map, the higher the relevance with each unitpackage, the higher the priority degree of switching. Further, similarmaps are prepared in advance for other groups of packages such as thesunlight conditions.

Further, the priority degree of a group of packages in which a unitpackage has been switched may be determined in advance. FIG. 14 is a mapshowing the priority degree of a group of packages in which a unitpackage has been switched. In this map, the smaller the numerical valuein the column in which a group of packages is described, the higher thepriority degree by which the unit packages are switched. In this case,the package selecting part 90 preferentially switches a unit package ofa group of packages with a high priority degree when selecting a newdriving assistance package.

The maps of FIG. 13 and FIG. 14 are stored in the ROM of the electroniccontrol unit 80. Note that the maps of FIG. 13 and FIG. 14 are justillustrations. The priority degrees in the maps may be different fromthose shown. Further, the priority degrees shown in the maps may beperiodically updated by wireless communication with the outside of thevehicle 1. In this case, the maps are stored in the RAM of theelectronic control unit 80.

After step S205, the control routine is ended. Note that, at step S202,the package selecting part 90 may determine the driving assistancepackage based on at least one of the surrounding environmentinformation, home vehicle information, and driver information.

Rejection Count Detection Processing

Below, referring to the flow chart of FIG. 15, rejection count detectionprocessing will be explained. FIG. 15 is a flow chart showing thecontrol routine of rejection count detection processing in the firstembodiment of the present invention. The control routine is repeatedlyperformed by the electronic control unit 80 at predetermined timeintervals while the driver selects the automated driving mode.

First, at step S301, the rejection count detecting part 93 judgeswhether the driving assistance package proposed by the package proposingpart 91 had not been approved by the driver in the period from when stepS301 had been performed the previous time to when step S301 is performedthe current time. IF it is judged that the driving assistance packageproposed by the package proposing part 91 was not approved by thedriver, the control routine proceeds to step S303.

At step S303, 1 is added to the rejection count Cn of the not approveddriving assistance package. The initial value of the rejection count Cnwhen the vehicle 1 is not yet used is zero. The rejection count Cn isstored in the RAM of the electronic control unit 80. “n” of therejection count Cn is the number corresponding to the not approveddriving assistance package. After step S303, the control routine isended.

On the other hand, if at step S301 the driving assistance packageproposed by the package proposing part 91 is approved by the driver orthe driver did not perform an approval operation in the period from whenstep S301 was executed the previous time to when step S301 is executedthe current time, the control routine proceeds to step S302.

At step S302, the rejection count detecting part 93 judges whether aninput operation by the driver was performed in the period from executionof step S301 the previous time to execution of step S301 the currenttime. If it is judged that an input operation by the driver wasperformed, the control routine proceeds to step S303.

At step S303, the rejection count detecting part 93 adds 1 to therejection count Cn of the driving assistance package which had been usedwhen the driver performed the input operation. The “n” of the rejectioncount Cn is a number corresponding to the driving assistance packagewhich had been used when the input operation by the driver wasperformed. After step S303, the control routine is ended.

On the other hand, if at step S302 it was judged that an input operationby the driver had not been performed, the control routine is ended.

Note that, the order of step S301 and step S302 may be reversed.Further, either of step S301 and step S302 may be omitted.

Second Embodiment

The configuration and control of the automated driving system accordingto the second embodiment are basically similar to the configuration andcontrol of the automated driving system according to the firstembodiment except for the points explained below. For this reason,below, the second embodiment of the present invention will be explainedfocusing on the parts different from the first embodiment.

In the second embodiment, the package selecting part 90 selects adriving assistance package in which performance of driving assistanceoperations for which performance had been obstructed by an inputoperation performed by the driver is not permitted, if the rejectioncount of the driving assistance package determined based on at least oneof the surrounding environment information, vehicle information, anddriver information is a threshold value or more. Due to this, it ispossible to propose to the driver a driving assistance package betterreflecting the preferences of the driver.

Priority Degree Changing Processing

In the second embodiment, in addition to the control routines shown inFIG. 11, FIG. 12, and FIG. 15, the control routine shown in FIG. 16 isperformed. FIG. 16 is a flow chart showing the control routine ofpriority degree changing processing in the second embodiment of thepresent invention. This control routine is repeatedly performed by theelectronic control unit 80 at predetermined time intervals while theautomated driving mode is selected by the driver.

First, at step S401, the package selecting part 90 judges whether aninput operation by the driver was performed in the period from when stepS401 was executed the previous time to when step S401 is executed thecurrent time. If it was judged that an input operation by the driver wasnot performed, the control routine is ended. On the other hand, if itwas judged that an input operation by the driver was performed, thecontrol routine proceeds to step S402.

At step S402, the package selecting part 90 identifies the drivingassistance package which had been used when the input operation by thedriver was performed. Next, at step S403, the package selecting part 90identifies the driving assistance operations which had been performedwhen the input operation by the driver was performed.

Next, at step S404, the package selecting part 90 changes the prioritydegree of the driving assistance package newly selected when therejection count of the driving assistance package identified at stepS402 is a threshold value or more. At this time, the package selectingpart 90 raises the priority degree of the driving assistance package inwhich performance of the driving assistance operations identified atstep S403 was not permitted.

As shown in FIG. 5, in the unit package of “snow”, performance of lanetracking control is permitted, while in the unit packages of “heavyrain”, “heavy snow”, and “dense fog”, performance of lane trackingcontrol is not permitted. Further, as shown in FIG. 13, in the column ofunit packages of “snow”, among the unit packages of “heavy rain”, “heavysnow”, and “dense fog”, “heavy snow” is the highest in priority degree.For this reason, for example, when lane tracking control for whichperformance is permitted in the driving assistance package in which theunit package of “snow” had been combined is being performed, if an inputoperation by the driver was performed, the package selecting part 90switches “rain” and “heavy snow” in the column of the unit package of“snow” in the map of FIG. 13. Note that, in this case, the map of FIG.13 is stored in the RAM of the electronic control unit 80.

After step S404, the control routine is ended.

Third Embodiment

The configuration and control of the automated driving system accordingto the third embodiment are basically similar to the configuration andcontrol of the automated driving system according to the firstembodiment except for the points explained below. For this reason,below, the third embodiment of the present invention will be explainedfocusing on the parts different from the first embodiment.

FIG. 17 is a block diagram showing the configuration of an automateddriving system 100′ of a vehicle according to the third embodiment ofthe present invention. The automated driving system 100′ is furtherprovided with a driver identifying part 94 identifying the driver of thevehicle 1 based on driver information. The driver information isacquired by the driver information acquiring device 30.

In the third embodiment, the rejection count detecting part 93 judgeswhether performance of the driving assistance operations for whichperformance is permitted in the driving assistance package has beenrejected by the driver identified by the driver identifying part 94, anddetects the number of times performance of the driving assistanceoperations for which performance is permitted in the driving assistancepackage was rejected by the driver identified by the driver identifyingpart 94 as the rejection count of the driving assistance package.Further, the package selecting part 90 selects a driving assistancepackage different from that driving assistance package, if the rejectioncount of the driving assistance package detected by the rejection countdetecting part 93 is the threshold value or more. For this reason, inthe third embodiment, even if the vehicle 1 is used by a plurality ofdrivers, driving assistance packages matching the preferences of thedifferent drivers can be proposed.

Rejection Count Detection Processing

In the third embodiment, instead of the control routine shown in FIG.15, the control routine shown in FIG. 18 is executed. FIG. 18 is a flowchart showing a control routine of the rejection count detectionprocessing in the third embodiment of the present invention. The controlroutine is repeatedly performed by the electronic control unit 80 atpredetermined time intervals while the driver selects the automateddriving mode. In FIG. 18, step S501 and step S502 are similar to stepS301 and step S302 in FIG. 15, so explanations will be omitted.

If at step S501 it is judged that the driving assistance packageproposed by the package proposing part 91 was not approved by thedriver, or if at step S502 it was judged that an input operation by thedriver was performed, the control routine proceeds to step S503.

At step S503, the driver identifying part 94 identifies the driver ofthe vehicle 1 based on the driver information. The driver information isacquired by the driver information acquiring device 30. The driveridentifying part 94, for example, compares the facial expression of thedriver detected by the driver monitor camera 31 with the facialexpressions of drivers stored in advance in the ROM to thereby identifythe driver of the vehicle 1.

Next, at step 5504, the rejection count detecting part 93 adds 1 to therejection count Cn,m of the driving assistance package. The “n” of therejection count Cn,m is a number corresponding to the driving assistancepackage which was not approved or the driving assistance package whichwas used when the input operation by the driver was performed. Further,the “m” of the rejection count Cn,m is a number corresponding to thedriver identified at step S503. After step S504, the control routine isended.

Driving Assistance Package Selection Processing

Further, in the third embodiment, at step S102 of FIG. 11, instead ofthe control routine shown in FIG. 12, the control routine shown in FIG.19 is executed. FIG. 19 is a flow chart showing the control routine ofdriving assistance package selection processing in the third embodimentof the present invention. In FIG. 19, step S601, step S602, step S605,and step S606 are similar to step S201, step S202, step S204, and stepS205 in FIG. 12, so explanations will be omitted.

After step S602, the control routine proceeds to step S603. At stepS603, in the same way as step S503 of FIG. 18, the driver identifyingpart 94 identifies the driver of the vehicle 1 based on the driverinformation. Next, at step S604, the package selecting part 90 judgeswhether the rejection count Cn,m of the driving assistance packagedetermined at step S602 is less than the threshold value Cth. Therejection count Cn,m is detected by the rejection count detecting part93 in the control routine of the rejection count detection processing ofFIG. 18. The “n” of the rejection count Cn,m is a number correspondingto the driving assistance package which was determined at step S602.Further, the “m” of the rejection count Cn,m is a number correspondingto the driver identified at step S603.

If at step 5604 it was judged that the rejection count Cn,m is less thanthe threshold value Cth, the control routine proceeds to step S605. Onthe other hand, when at step S604 it was judged that the rejection countCn,m is the threshold value Cth or more, the control routine proceeds tostep S606.

Above, preferred embodiments according to the present invention wereexplained, but the present invention is not limited to these embodimentsand can be corrected and changed in various ways within the scope of theclaims. For example, in the above-mentioned embodiments, the drivingassistance package is determined by combining unit packages selectedbased on the surrounding environment information etc., but the drivingassistance package may be determined from combinations of unit packagesdetermined in advance based on the surrounding environment informationetc. In this case, for each driving assistance package, the prioritydegree of the newly selected driving assistance package is stored in theROM or RAM of the electronic control unit 80.

Further, the above-mentioned embodiments can be carried out in anycombinations. For example, the control routine shown in FIG. 16 may beperformed in the third embodiment.

REFERENCE SIGNS LIST

-   1. vehicle-   10. surrounding environment information acquiring device-   20. vehicle information acquiring device-   30. driver information acquiring device-   80. electronic control unit-   90. package selecting part-   91. package proposing part-   92. automated driving executing part-   93. rejection count detecting part-   94. driver identifying part-   100, 100′. automated driving system

What is claimed is:
 1. A vehicle automated driving system comprising: asurrounding environment information acquiring device configured toacquire surrounding environment information relating to surroundingenvironment conditions of the vehicle, a vehicle information acquiringdevice configured to acquire vehicle information relating to conditionsof the vehicle, a driver information acquiring device configured toacquire driver information relating to conditions of a driver of thevehicle, a package selecting part configured to select a drivingassistance package, wherein the driving assistance package packagespermissions for each of a plurality of driving assistance operations andpermits at least one of the plurality of driving assistance operationsto be performed, a package proposing part configured to propose thedriving assistance package selected by the package selecting part to thedriver, an automated driving executing part configured to executedriving assistance operations for which performance is permitted in thedriving assistance package proposed by the packaging proposing part andapproved by the driver, and a rejection count detecting part configuredto judge whether the driver has rejected performance of individualdriving assistance operations for which performance is permitted in adriving assistance package and detect the number of times the driver hasrejected performance of the individual driving assistance operations forwhich performance is permitted in the driving assistance package as therejection count of the driving assistance package, wherein the packageselecting part is configured to determine one driving assistance packagefrom a plurality of driving assistance packages based on at least one ofthe surrounding environment information, the vehicle information, andthe driver information, select the determined driving assistance packageif the rejection count of the determined driving assistance package isless than a predetermined threshold value, and select a differentdriving assistance package that is different from the determined drivingassistance package if the rejection count of the determined drivingassistance package is the threshold value or more, and the plurality ofdriving assistance operations include at least one of vision assistancefunctions and congestion assistance functions.
 2. The vehicle automateddriving system according to claim 1, wherein the rejection countdetecting part is configured to judge that performance of the individualdriving assistance operations for which performance is permitted in thedriving assistance package has been rejected by the driver, if thedriving assistance package proposed by the package proposing part wasnot approved by the driver.
 3. The vehicle automated driving systemaccording to claim 1, wherein the rejection count detecting part isconfigured to judge that performance of the individual drivingassistance operations for which performance is permitted in the drivingassistance package has been rejected by the driver, if performance ofdriving assistance operations for which performance is permitted in thedriving assistance package was obstructed by an input operationperformed by the driver.
 4. The vehicle automated driving systemaccording to claim 2, wherein the rejection count detecting part isconfigured to judge that performance of the individual drivingassistance operations for which performance is permitted in the drivingassistance package has been rejected by the driver, if performance ofdriving assistance operations for which performance is permitted in thedriving assistance package was obstructed by an input operationperformed by the driver.
 5. The vehicle automated driving systemaccording to claim 3, wherein the input operation performed by thedriver is at least one of acceleration, steering, and braking.
 6. Thevehicle automated driving system according to claim 4, wherein the inputoperation performed by the driver is at least one of acceleration,steering, and braking.
 7. The vehicle automated driving system accordingto claim 3, wherein the package selecting part is configured to selectthe different driving assistance package based on which performance ofdriving assistance operations was obstructed by the input operationperformed by the driver.
 8. The vehicle automated driving systemaccording to claim 4, wherein the package selecting part is configuredto select the different driving assistance package based on whichperformance of driving assistance operations was obstructed by the inputoperation performed by the driver.
 9. The vehicle automated drivingsystem according to claim 5, wherein the package selecting part isconfigured to select the different driving assistance package based onwhich performance of driving assistance operations was obstructed by theinput operation performed by the driver.
 10. The vehicle automateddriving system according to claim 6, wherein the package selecting partis configured to select the different driving assistance package basedon which performance of driving assistance operations was obstructed bythe input operation performed by the driver.
 11. The vehicle automateddriving system according to claim 1, wherein the system furthercomprises a driver identifying part configured to identify the driver ofthe vehicle based on the driver information, and the rejection countdetecting part is configured to judge whether performance of theindividual driving assistance operations for which performance ispermitted in a driving assistance package has been rejected by thedriver identified by the driver identifying part, and detect the numberof times performance of the individual driving assistance operations forwhich performance is permitted in the driving assistance package hasbeen rejected by the driver identified by the driver identifying part asthe rejection count of the driving assistance package.
 12. A vehicleautomated driving system for a vehicle, comprising: at least one firstsensor that acquires surrounding environment information relating tosurrounding environment conditions of the vehicle; at least one secondsensor that acquires vehicle information relating to conditions of thevehicle; at least one third sensor that acquires driver informationrelating to conditions of a driver of the vehicle; and an electroniccontrol unit (ECU) including at least one processor programmed to:select a driving assistance package, wherein the driving assistancepackage packages permissions for each of a plurality of drivingassistance operations to be performed during an automated driving modeand permits at least one of the plurality of driving assistanceoperations to be performed during the automated driving mode, proposethe driving assistance package that was selected to the driver, executethe automated driving mode which includes driving assistance operationsthat are permitted in the proposed driving assistance package that hasbeen approved by the driver, and judge whether the driver has rejectedperformance of individual driving assistance operations that arepermitted in a driving assistance package and detect the number of timesthe driver has rejected performance of the individual driving assistanceoperations that are permitted in the driving assistance package as therejection count of the driving assistance package, wherein thedetermination of the driving assistance package from among a pluralityof driving assistance packages is based on at least one of thesurrounding environment information, the vehicle information, and thedriver information, the determined driving assistance package isselected if the rejection count of the determined driving assistancepackage is less than a predetermined threshold value, and a differentdriving assistance package that is different from the determined drivingassistance package is selected if the rejection count of the determineddriving assistance package is the threshold value or more, and theplurality of driving assistance operations include at least one ofvision assistance functions and congestion assistance functions.